Feature: HandlingSchedulingConflictsAs an operator I want to make sure feature conflicts are managed by an appropriate policy.
Background:
Given a system with no active work items
And a work item named I1 scheduled to start at 10:00, last for 15 minutes, and use R1And a work item named I2 scheduled to start at 10:10, last for 5 minutes, and use R1And a first one wins conflict resolution approach
Scenario: Nothing going on
When now is 9:59Then there should be no active items
Scenario: One item active
When now is 10:01ThenI1 should be active
Scenario: ConflictResolvedWhen now is 10:10ThenI1 should be active
AndI2 should be blocked
Scenario: DelayedStartGiven now is 10:00When now is 10:16ThenI1 should be completed
AndI2 should be active
Scenario: Delayed finished
Given now is 10:00And now is 10:15When now is 10:21ThenI2 should be completed
After Removing All Extra Time "Movement" Steps
Feature: HandlingSchedulingConflictsAs an operator I want to make sure feature conflicts are managed by an appropriate policy.
Background:
Given a system with no active work items
And a work item named Megatron_Torso scheduled to start at 10:00, last for 15 minutes, and use 3d_printer_1
And a work item named Megatron_Head scheduled to start at 10:10, last for 5 minutes, and use 3d_printer_1
And a first one wins conflict resolution approach
Scenario: Nothing going on
When now is 9:59Then there should be no active items
Scenario: One item active
Given now is 9:59When the time becomes 10:01ThenMegatron_Torso should be active
Scenario: ConflictResolvedWhen now is 10:10ThenMegatron_Torso should be active
AndMegatron_Head should be blocked
Scenario: DelayedStartGiven now is 10:00When the time becomes 10:16ThenMegatron_Torso should be completed
AndMegatron_Head should be active
Scenario: Delayed work item finishes late
Given now is 9:59When the time becomes 10:21ThenMegatron_Head should be completed
After Gojko's Twitter Comment
It's amazing what 140 characters can accomplish. He did it in fewer than that.
Feature: HandlingSchedulingConflictsAs an operator I want to make sure feature conflicts are managed by an appropriate policy.
Background:
Given an empty schedule
And a work item named Megatron_Torso scheduled to start at 10:00, last for 15 minutes, and use 3d_printer_1
And a work item named Megatron_Head scheduled to start at 10:10, last for 5 minutes, and use 3d_printer_1
And a first one wins conflict resolution approach
And the business time is 9:59Scenario: Nothing going on
Then there should be no active items at 9:59Scenario: One item active
ThenMegatron_Torso should be active at 10:01Scenario: ConflictResolvedThenMegatron_Torso should be active at 10:10AndMegatron_Head should be blocked
Scenario: DelayedStartThenMegatron_Torso should be completed at 10:16AndMegatron_Head should be active
Scenario: Delayed work item finishes late
ThenMegatron_Head should be completed at 10:21
Before
After Removing All Extra Time "Movement" Steps
After Gojko's Twitter Comment
It's amazing what 140 characters can accomplish. He did it in fewer than that.